home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20021006-20030409
/
000347_jaltman2@nyc.rr.com_Sun Mar 2 13:47:36 EST 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
4KB
|
76 lines
Article: 14144 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!phl-feed.news.verio.net!iad-feed.news.verio.net!iad-peer.news.verio.net!news.verio.net!news.maxwell.syr.edu!newsfeed-east.nntpserver.com!nntpserver.com!news-west.rr.com!news-server.columbus.rr.com!cyclone.rdc-nyc.rr.com!news-out.nyc.rr.com!twister.nyc.rr.com.POSTED!not-for-mail
From: "Jeffrey Altman [Road Runner NYC]" <jaltman2@nyc.rr.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-DOS Kermit
References: <20030301.1833.31585snz@aral.vorkosigan.co.uk> <smJqS8E+f8CK@cc.usu.edu>
In-Reply-To: <smJqS8E+f8CK@cc.usu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 53
Message-ID: <6no8a.49308$Mh3.17650633@twister.nyc.rr.com>
Date: Sun, 02 Mar 2003 14:16:34 GMT
NNTP-Posting-Host: 66.108.138.151
X-Complaints-To: abuse@rr.com
X-Trace: twister.nyc.rr.com 1046614594 66.108.138.151 (Sun, 02 Mar 2003 09:16:34 EST)
NNTP-Posting-Date: Sun, 02 Mar 2003 09:16:34 EST
Organization: Road Runner - NYC
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14144
Joe Doupnik wrote:
> In article <20030301.1833.31585snz@aral.vorkosigan.co.uk>, mike@aral.vorkosigan.co.uk (Michael Bernardi) writes:
>
> There is a bit of ANSI terminal emulation on MSK. There is a lack
> of information here as to just what ANSI or SCO ANSI <etc> actually contain
> in detail. Also I don't have an SCO machine to be a local reference. A
> formal reference is really required with terminal emulation development.
The SCO Console implementation of ANSI is fairly well documented in the
man pages of the SCO Unix distribution.
The same is true for the AT386 Console driver used for other commercial
variants of x86 Unix.
The Linux console driver is a mess as it has been altered and extended
with each and every kernel release.
If you have any questions about how these emulations should behave, just
ask.
> On SSH. That's a rather large can of wiggly things. MSK has no
> crypto support, the laws on export have been difficult for everyone. And,
> to be candid here, my readings of SSH source code a couple of years ago
> caused me to shun the item completely on Unix systems. Maybe I overreacted
> and need an education. In any case, memory space is at a premium with MSK
> so whatever is done needs to be quite small and uncomplicated and to always
> yield a usable connection even if the other side proves difficult.
SSH has been implemented on the Palm. You need to focus on implementing
a very small number of crypto algorithms. Most likely just 3DES since
that is implemented in all distributions. The SSH code that became the
basis for OpenSSH is quite ugly. However, the code does not represent
the protocol. See the Internet-Drafts that will finally become RFCs
this month.
> On my gear there is a sprinkling of SSL stuff for web work, no SSH,
> no r* utilities, and no paranoia about wire snoops. Keeping certificates
> straight is enough bother, and openssl isn't very nice about that.
OpenSSL is not a certificate manager. It is up to the application to
perform the certificate management for the user. Unfortunately, there
is no standard certificate manager on Unix and I never finished my
implementation for one on Windows.
> Guidance and views on the above items are certainly welcomed. I
> don't mean to appear reactionary on these matters, but also I don't believe
> 95% of the claims folks advance for crypto features. Old simple XOR-ing
> probably does as well to keep away casual packet snoopers.
If only that were true.
> Joe D.